Bridge indexer #17870
Bridge indexer #17870
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
| txn_hash bytea NOT NULL, | ||
| gas_usage BIGINT NOT NULL, | ||
| data_source TEXT NOT NULL, | ||
| PRIMARY KEY(chain_id, nonce, status) |
There was a problem hiding this comment.
why is status part of the key? that seems excessive to me, thoughts?
I would expect the table to be used with a key that represents everything that has happened to a given bridged asset, as such all statuses should be returned no?
There was a problem hiding this comment.
actually reading some more about composite key I see that we cannot use the chain_id, nonce only (I guess we have multiple entries for sui?).
However I do wonder what is the value of this primary key and thinking that some proper indexes may be better.
Unless I do not understand how a primary key is used or can be used here
| @@ -0,0 +1,26 @@ | |||
| CREATE TABLE token_transfer_data | |||
There was a problem hiding this comment.
should we have more info into this table so that it can be queried on its own?
for instance we have no timestamp which makes time query only possible with a join (e.g. highest amount in the past week).
Also maybe sender and recipient address are more interesting indexes?
dariorussi
force-pushed
the
bridge-indexer
branch
from
9d68e89
to
f98c901
Compare
Description
Adds the sui-bridge-indexer crate.